From: Aleksey Kladov <aleksey.kladov@gmail.com>
Date: Wed, 2 May 2018 15:13:03 +0000 (+0300)
Subject: Explain why we need a `Vec<Dependency>` in `Resolve`.
X-Git-Tag: archive/raspbian/0.35.0-2+rpi1~3^2^2^2^2^2^2^2~22^2~1^2~26^2
X-Git-Url: https://dgit.raspbian.org/%22http://www.example.com/cgi/success//%22http:/www.example.com/cgi/success/?a=commitdiff_plain;h=20d8ff4fecf898c1028f66945d62877989bb70d5;p=cargo.git

Explain why we need a `Vec<Dependency>` in `Resolve`.
---

diff --git a/src/cargo/core/resolver/resolve.rs b/src/cargo/core/resolver/resolve.rs
index db4a5b5ee..728f693bf 100644
--- a/src/cargo/core/resolver/resolve.rs
+++ b/src/cargo/core/resolver/resolve.rs
@@ -18,6 +18,9 @@ use super::encode::Metadata;
 /// for each package.
 #[derive(PartialEq)]
 pub struct Resolve {
+    /// A graph, whose vertices are packages and edges are dependency specifications
+    /// from Cargo.toml. We need a `Vec` here because the same package
+    /// might be present in both `[dependencies]` and `[build-dependencies]`.
     graph: Graph<PackageId, Vec<Dependency>>,
     replacements: HashMap<PackageId, PackageId>,
     reverse_replacements: HashMap<PackageId, PackageId>,